Pos printing triggered by pharmacy prescription orders

ABSTRACT

The invention provides a computer implemented system and method for printing at a POS, comprising: 
     determining in a PM CS of a pharmacy of a retail store a payloadID to association with a prescription order for a prescription ordered from said pharmacy; 
     filling, in said pharmacy, said prescription, to provide a filled prescription; 
     first printing, using a PM CS printer in said pharmacy, a first print that encodes first information associated with said filled prescription; 
     attaching or physically associating with hardware or adhesive said first print with said filled prescription; 
     during a purchase transaction in which said prescription is being purchased at a POS terminal of a POS CS of said retail store, reading said first print to determine said first information associated with said filled prescription; 
     during said purchase transaction, using data lines for retrieving second information associated with said first information; and 
     during said purchase transaction, second printing, using a printer at a POS of said POS CS, a second print including said second information in human understandable form.

CROSS REFERENCE TO RELATED APPLIATIONS

This application claims priority to provisional application 60/942,247,filed Jun. 6, 2007, attorney docket number PIP194ROBEP-US.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The field of the invention is POS computer systems.

2. Background

U.S. Pat. No. 6,304,849 discloses a method and system for printing acombination pharmaceutical label and directed newsletter. U.S. Pat. No.6,240,394 discloses a method and apparatus for automatically generatingadvisory information for pharmacy patients. U.S. Pat. No. 6,067,524discloses a method and system for automatically generating advisoryinformation for pharmacy patients along with normally transmitted data.U.S. Pat. No. 6,321,210 discloses a method and apparatus for selectivedistribution of discount coupons.

This invention relates to pharmacy management computer systems andretail store point of sale computer systems.

ACRONYMS AND ABBREVIATIONS USED HEREIN

-   CS—Computer System-   PM CS Pharmacy Management Computer System-   Retail Store—RS-   NDC—National Drug Code-   UPC—Universal Product Code-   POS—Point of Sale-   POS CS—Point of Sale Computer System-   ID—Identification-   CID—Consumer ID-   RSID—Retail Store ID-   PatID—Patient ID-   ProdID—Product ID-   PresID—Prescription ID-   DrugID—Identification of a drug-   PayloadID—Payload Identification-   EncPresID—Encrypted Prescription ID-   EncPatID—Encrypted Patient ID-   Qnty—Quantity-   BF—Bland Field-   TID—Transaction ID

DEFINITIONS USE HEREIN

A CS means one or more computers having commonly accessible datastorage.

A computer means at least an input device for inputting data, a centralprocessing unit for processing data, a memory for storing data, and anoutput device for outputting data.

A POS CS is a CS designed to log purchase transactions occurring in astore at least one POS, and to track inventory for the store.

A PM CS is a computer system designed to log and track prescriptionorders in a pharmacy and track pharmacy medication inventory.

UPCs mean any set of codes each one uniquely identifying a product.

OBJECTS OF THE INVENTION

It is an object of this invention to enable a retail store to processpurchase transactions including purchase of prescriptions.

It is an object of this invention to enable a retail store to printpayloads based upon pharmacy prescription data for a prescription orderbeing purchased.

SUMMARY OF THE INVENTION

This application provides methods and systems to enable a POS CS of aretail store having a pharmacy to process purchase transactionsincluding purchase of prescriptions filled by the pharmacy, at a POS,and to enable a printer at the POS to print payloads during thatpurchase transaction that are based upon pharmacy prescription data fora prescription order being purchased in the transaction. A payload isprinted information intended for the person purchasing the prescription.

In a first embodiment, the PM CS responds to receipt of a prescriptionorder by storing information including a payloadID on a recording media,such as in a printed bar code printed on paper or magnetization patternimposed in magnetic media, for the prescription order. A person ormachine attaches the recording media to the filled prescription for thatprescription order. The recording media and filled prescription are thenpresented at a POS of the POS CS, for purchase of the filledprescription. During a transaction to purchase the filled prescription,the POS CS reads the payloadID at the POS. The POS CS previously storedan association of payloadIDs to payloads. The POS CS identifies thepayload associated therein with the payloadID read from the recordingmedia and prints that payload during the purchase transaction involvingthe prescription.

In a second embodiment, the PM CS stores in the PM CS memory a uniquerecord identifier (RecordID) in association with each record of data foreach prescription order. The PM CS also stores the RecordID on recordingmedia, such as a printed bar code printed on paper or a magnetizationpattern imposed in magnetic media. A person or a machine attaches therecording media to the filled prescription. The recording media andfilled prescription are then presented at a POS of the POS CS, forpurchase of the filled prescription. During the transaction to purchasethe filled prescription, the POS CS reads the RecordID at the POS. Then,the POS CS transmits the RecordID to the PM CS. In response, the PM CSretrieves from memory certain information from the PM CS prescriptionorder record associated with that recordID and transmits that retrievedcertain information to the POS CS. That certain information includes apayloadID. The POS CS identifies the payload associated with thereceived payloadID and prints that payload during the purchasetransaction involving the prescription.

In the first and second embodiments, the POS CS preferably receives fromthe PM CS during the transaction for purchase of the filledprescription: Prescription ID; Copay amount; NDC; and Department number.In the first embodiment, that information is encoded in the recordingmedia attached to the filled prescription. Attaching is by means ofhardware such as bags, staples, clips, or by adhesives, such as stickytape or glues. In the second embodiment, that information may all beretrieved to the POS CS from the PM CS during the transaction inresponse to the PM CS receiving the RecordID.

In a first alternative, a payloadID corresponds to informationassociated in the PM CS with the prescription order.

For example, in the first alternative, the payloadID may correspond to adrug identification (drugID), such as an NDC for the drug specified inthe prescription order. In this example, a payloadID is a drugID or anencrypted version of the DrugID, and the drugID may be an NDC. The PM CSassociates with each prescription order, the payloadID corresponding tothe drug identified in the prescription order. The corresponding payloadprovides printed information about the drug specified by theprescription, and optionally additional information, possibly includingone or more purchase incentive offers for purchase of a product.

A purchase incentive offer is an offer for a benefit, such as adiscount, upon purchase of a specified product.

In other examples of the first alternative, the payloadID corresponds tosome value for some piece of information in the PM CS associated withthe prescription order, or the payloadID corresponds to a combination ofvalues for plural pieces of information in the PM CS associated with theprescription order. These pieces of information are generally defined intable 1, and are as follows: DrugID; DoctorID; NewRX; RefillRX;Refill#RX; PaymentType; Date processed; Time processed; NDC; MedicationName; Customer Name; Age; Date of Birth; Gender; Script Status; Payor;Payor Code; RX Number; Dispensed Qty; Refill Sequence; LanguageIndicator; Daily Supply; Days Supply; Original Fill Date; Expires Date;Refills Remaining; Unique Patient ID; Dr. Number; Monograph; State Code;Region; Retailer Division; Retailer Store; Patient Directions;Pharmacist Directions; NCPDP ID Number; BIN No.; Control No.; Agency;Group; Plan; Name Mask; Medicaid; Opt Out (HIPAA); and Duplicate. Thecorresponding payload provides printed information relating in some wayto one or more of the values for the plural pieces of information in thePM CS associated with the prescription order, possibly including one ormore purchase incentive offers for purchase of a product.

For instances where the payload is related to only one piece ofinformation in the prescription order, the payloadID may be the valuefor that piece of information, or an encrypted version of that value.For example, the PayloadID may be any of the values or encryptedversions thereof for fields: DrugID; DoctorID; NewRX; RefillRX;Refill#RX; PaymentType; Date processed; Time processed; NDC; MedicationName; Customer Name; Age; Date of Birth; Gender; Script Status; PayorCode; RX Number; Dispensed Qty; Refill Sequence; Language Indicator;Daily Supply; Days Supply; Original Fill Date; Expires Date; RefillsRemaining; Unique Patient ID; Number; Monograph; State Code; Region;Retailer Division; Retailer Store; Patient Directions; PharmacistDirections; NCPDP ID Number; BIN No.; Control No.; Agency; Group; Plan;Name Mask: Medicaid; Opt Out (HIPAA); and Duplicate.

In a second alternative, a payloadID corresponds to a patientinformation (PatID). A PatID is associated with prescription orderreceived in the pharmacy for the corresponding patient. In thisalternative, the payloadID may be the PatID stored in the PM CS records,or an encrypted version of that PatID, EncPatID. In this alternative,the payload stored in the POS CS in association with the payloadID mayhave been predetermined based at least in part upon values forinformation in the PM CS associated with the prescription order from thesame patient's prior prescription orders, or based upon such values forthe patient's prior and current prescription orders. The values uponwhich the payload and payloadID are based are values for the same fieldsnoted above as included in a record in the PM CS for a prescriptionorder. The predetermination may be determined by any CS having access toat least part of the PM CS's patient records. The CS may be the PM CS ora central CS. That CS then transmits the payloadID to payloadassociation to the POS CS where it is stored until the payloadID is readby the POS CS during a purchase transaction. The payload may include apurchase incentive offer, product (including drug product) advertising,and safety and use information about a drug associated with theprescription order.

In a variation on the second alternative where the PM CS performs theanalysis and determination of payloadID to payload associations, thepayloadID may correspond to a RecordID, Encrypted RecordID, PresID, orEncPresID.

In a preferred embodiment, the POS CS receives the co-payment to thecurrent ongoing transaction involving the scanned prescription bar codeand applies that co-payment to the transaction.

In a preferred embodiment, the POS CS does not save the PresID after thetransaction is concluded.

In a preferred embodiment, the POS CS does save the recordID inassociation with other information for the transaction.

In a third embodiment, the POS CS requests from the PM CS an EncPatIDassociated with data it reads from papers attached to a filledprescription being purchased at a POS. Then, the POS CS uses theretrieved EncPatID as a PayloadID to determine if it has a Payloadassociated therewith. If so, it prints the payload if other conditionsare met. In the third embodiment, the POS CS receives from the PM CSduring the transaction, the EncPatID.

In a preferred embodiment, the POS CS captures, during purchasetransactions, associations of EncPatID to NDC code, stores thatinformation, and transmits that information to a central CS. The centralCS analyzes the information and transmits back to the POS CS payloadIDsand associated payloads. Alternatively, the PM CS may perform thesefunctions of the central CS.

In one aspect, the invention provides a system and computer implementedmethod for printing at a POS, comprising: determining in a PM CS of apharmacy of a retail store a payloadID to association with aprescription order for a prescription ordered from said pharmacy;filling, in said pharmacy, said prescription, to provide a filledprescription; first printing, using a PM CS printer in said pharmacy, afirst print that encodes first information associated with said filledprescription; attaching or physically associating with hardware oradhesive said first print with said filled prescription; during apurchase transaction in which said prescription is being purchased at aPOS terminal of a POS CS of said retail store, reading said first printto determine said first information associated with said filledprescription; during said purchase transaction, using data lines forretrieving second information associated with said first information;and during said purchase transaction, second printing, using a printerat a POS of said POS CS, a second print including said secondinformation in human understandable form.

BRIEF DESCRIPTION OF THE DRAWING

FIG. 1 is a schematic view of a computer network 1;

FIG. 2 is a schematic view of structure of retail store 30 of FIG. 1;

FIG. 3 is a schematic view of PM CS 60 of FIG. 2;

FIG. 4 is a schematic view of POS CS 70 of FIG. 2;

FIGS. 5A and 5B are a schematic design view of novel data structures ofPM CS 60;

FIG. 6 is a schematic design view of novel data structures of POS CS 70;

FIG. 7 is a schematic design view of novel data structures of central CS10 of FIG. 1;

FIG. 8 is a flow chart showing initial steps of various methodembodiments;

FIG. 9 is a flow chart showing steps of the first embodiment subsequentto those described in FIG. 8;

FIG. 10 is a flow chart showing steps of the second embodimentsubsequent to those described in FIG. 8; and

FIG. 11 is a flow chart showing steps of the third embodiment subsequentto those described in FIG. 8.

DETAILED DESCRIPTION Structures

FIG. 1 shows a computer network including central CS 10, network 20,such as the Internet, and retail stores 30, 40, and 50. Lines connectingthese elements represent data communication links, whether wired orwireless. Link 95 connects retail store 30 to network 20.

FIG. 2 shows retail store 30 including a region for use as a pharmacywherein resides PM CS 60, a region for use as a packaged goods storeincluding POS CS 70 having POS terminals 85 and 90, and a communicationlink 80 between PM CS 60 and POS CS 70. The pharmacy region may alsohave POS terminals connected to POS CS 70 therein. Communication link 80preferably is a packet switched network connection.

FIG. 3 shows elements of PM CS 60 including a CPU, memory, a PM terminalfor data input and output, a PM printer for printing, and a PM scannerfor scanning.

FIG. 4 shows elements of POS CS 70 including a first CPU, CPU 1, memorycontrolled by CPU1, a second CPU, CPU 2, and memory controlled by CPU2,a POS terminal, a first POS printer, POS printer 1, a second POSprinter, POS printer 2, and a POS scanner. The POS terminal, printers,and scanner are located at the POS. The POS terminal typically includesa visual display and a keyboard for viewing and entering data. The POSscanner typically is linked to the POS terminal so that data scanned bythe scanner is transmitted to the POS terminal. POS printer 1 typicallyprints register receipts for transactions as instructed by the POSterminal. POS printer 2 typically prints coupons and advertisements asinstructed by the second CPU, CPU2. CPU1 and CPU2 may share memory orcontrol their own memory, whether RAM or disk. In actual implementationsCPU1 controls purchase and inventory functions, and CPU 2 controlsmarketing functions. CPU2 may obtain data entered into a POS terminal bylistening in on the network line over which that data is transmitted toCPU1. CPU2 may control POS printer 2 to print marketing information,including the payloads discussed herein. Both POS printer 1, POS printer2, scanner, and the POS terminal are at the same POS. There may beseveral POSs each having their own terminals and printers in each retailstore.

Certain POS CS embodiments, have only a single printer at each POScapable of printing both register receipts and marketing materials andother information including the payloads discussed herein. Certainembodiments have a single CPU controlling both inventory and marketing.Certain embodiments have a CPU forming part of each POS terminalenabling the terminals to act independently of a CPU controlling storeinventory.

FIGS. 5A and 5B show design views of novel data structures in the memoryof PM CS 60 including a Pharmacy Patient Records Table 500, a DeIdentified Pharmacy Patient Records Table 510, Pharmacy Payload ID Table520, a Pharmacy Prescription Label Printer Table 530, a PharmacyAdditional Information Printer Table 540, a Pharmacy Stock Table 550, anEncrypted Patent ID table 560, and an Encrypted Prescription ID table570.

Pharmacy Patient Records Table 500 includes fields for PatID; PresID;Patient Information; NDC; Qnty; Order date; Filled Date; Purchase orDisposal Date; Copay amount; Department number; and recordID; and alsofor DoctorID; NewRX; RefillRX; Refill#RX; PaymentType; Date processed;Time processed; NDC; Medication Name; Customer Name; Age; Date of Birth;Gender; Script Status; Payor; Payor Code; RX Number; Dispensed Qty;Refill Sequence; Language Indicator; Daily Supply; Days Supply; OriginalFill Date; Expires Date; Refills Remaining; Unique Patient ID; Dr.Number; Monograph; State Code; Region; Retailer Division; RetailerStore; Patient Directions; Pharmacist Directions; NCPDP ID Number; BINNo.; Control No.; Agency; Group; Plan; Name Mask; Medicaid; Opt Out(HIPAA); and Duplicate.

DE Identified Pharmacy Patient Records Table 510 includes fields forEncPatID; EncPresID; BF; NDC; Qnty; Order date; Filled Date; Purchase orDisposal Date; Copay amount; Department number; and recordID, and alsothe fields from DoctorID to Duplicate noted above for table 500. Thatis, table 510 is a version of the patient record from which it is notpossible to identify the actual patient, unless one has access to theassociation of EncPatID to PatID, so that the patient record is“de-identified.” Table 510 is a version of patient prescription recordssuitable for transmission to central CS 10, because it is de-identified.

Pharmacy Payload ID Table 520 includes fields for EncPresID; NDC; Qnty;Payload ID: Date1; Date2; and recordID. The Pharmacy payload tableindicates what payloadID or payloadIDs to associate with a prescriptionorder and with the prescription order's recordID. In addition to NDC,Pharmacy PayloadID Table 520 may include fields for all of the otherdata elements in De Identified Pharmacy Patient Records Table 510.

Pharmacy Prescription Label Printer Table 530 includes fields forPresID; Prescription Label Information (Patient name, medicine name,dosing information); Bar Code encoding at least one of Payload ID andrecordID. Table 530 provides for encoding of the payloadID and/orrecordID in a bar code.

Pharmacy Additional Information Printer Table 540 includes fields forNDC; and Additional Information relating to NDC medication. Table 540allows PM CS 60 to print information relating to a drug in aprescription so that information can be attached to the prescriptionorder.

Pharmacy Stock Table 550 includes fields for NDC; Unit Type; and UnitQuantity in stock. Table 550 enables PM CS 60 to track its drugsinventory.

Encrypted Patent ID table 560 includes fields for PatID; and EncPatID.Table 560 enables PM CS 60 to relate an encrypted PatID back to thecorresponding PatID in table 500.

Encrypted Prescription ID table 570 includes fields for PresID; andEncPresID. Table 570 enables PM CS 60 to relate an EncPresID back to thecorresponding unencrypted PresID in tables 500, 510, and 520.

FIG. 6 shows design views of novel data structures in the memory of POSCS 70 including Prescriptions Payload Table 600; RS Transaction DataTable 610; and RS POS Stock and Price Table 620.

RS Payload Table 600 includes fields for PayloadID; Payload; Date1; andDate2. This table allows POS CS 70 to determine payloads to print frompayloadIDs. The date fields may be used to define a date range duringwhich the payload should be printed for a corresponding payloadID.

RS Transaction Data Table 610 includes fields for TID; CID; Date;ProdID1; ProdID1 Price; ProdID1 Qnty; ProdID2; ProdID2 Price; ProdID2Qnty; . . . ; Transaction Total Price; and Transaction Price Discounts.Here “. . . ” indicates additional product descriptions for additionalproducts associated with each transaction.

RS POS Stock and Price Table 620 includes fields for ProdID (UPC);Product Description; Stock Quantity; Price1; and Price2. This tableallows the retail store to keep track of its stock. Price1 and price2may reflect list price and discounted price for an item of a product.

FIG. 7 shows data structures in memory associated with central CS 10.These include many of the data structures similar to those associatedwith PM CS 60 and POS CS 70 wherein the only difference is an additionalretail store identifier (RSID) added to data from each retail store inorder to distinguish data from different retail stores from one another.These tables are: DE Identified Pharmacy Patient Records Table 510A;Pharmacy Payload ID Table 520A; Pharmacy Additional Information PrinterTable 540A; RS Payload Table 600A; and the RS Transaction Data Table610A.

FIG. 7 also shows additional data structures unique to central CS 10.Central CS 10 uses these tables to analyze and store prescriptioninformation and to determine payloads to associate with NDCs andencrypted prescription or PatIDs for a retail store. These includePayload Criteria Table 710; Payload Criteria Table 720; and CombinedPayload table 730.

Payload Criteria Table 710 includes fields for RSID; NDC; and Payload.This table enables central CS 10 to determine what payloads toassociated for NDCs for each retail store. Payload Criteria Table 710may also criteria for all of the other fields in De Identified PharmacyPatient Records Table 510A.

Payload Criteria Table 720 includes fields for NDC1; DATE1; NDC2; DATE2;NDC3; DATE3; . . . and Payload. This table provides criteria thatcentral CS 10 uses to determine what payload to associate with one ormore records of previously ordered prescriptions, a prescriptionhistory, associated with an identification, such as an encrypted PatID.CS 10 does so by determining if the prescription history meets thepurchases of NDC1, NDC2, NDC3, etc, in the time periods DATE1, DATE2,DATE3, etc. Payload Criteria Table 720 may also criteria for all of theother fields appearing in the De Identified Pharmacy Patient RecordsTable 510A.

In one example showing use by central CS 10 of its tables, it comparesprescription records in table 510A associated with a selected EncPatIDto a record in Payload Table 720. Central CS 10 determines if the NDCs(or any other drug identification) and dates or date ranges of order orpurchase, for records associated with an EncPatID, in table 510A, matchvalues for the NDCs and dates or date ranges in a record from thePayload Criteria table 720. If they do, then CS 10 associates thepayload identified in the record in Payload Criteria table 720 with theEncPatID and stores the association in a new record in Combined Payloadtable 730 along with the corresponding RSID. Central CS 10 may alsogenerate and store in the same record in Combined Payload table 730 apayloadID and dates for the fields date1 and date2. If central CSdetermines that the payload should only be provided upon purchase of acertain prescription order appearing in table 510A, it may also storethe corresponding EncPresID in the same record in Combined Payload Table730. The fields date1 and date2 may be used by the POS CS as start andend dates for period only during which the payload will be printed.

In another example showing use by central CS 10 of its tables, itcompares prescription records in table 510A associated with a selectedEncPatID to a record in Payload Table 720 as in the foregoing example,but also determines if the age field is greater than 30 and gender fieldis female. If so, it also provides an incentive for a medicine approvedfor treating bone mass loss.

In another example showing use by central CS 10 of its tables, itcompares prescription records in table 510A associated with a selectedEncPatID to a record in Payload Table 720 as in the foregoing example,but also determines if the “payor” field is “cash”. If so, it alsoprovides an incentive for a generic version of the medicine (which istypically less expensive) than the prescription's specified medicine.

In another example showing use by central CS 10 of its tables, itcompares prescription records in table 510A associated with a selectedEncPatID to a record in Payload Table 720 as in the foregoing example,but also determines if the “Dr. Number” is one of a specified set ofvalues. If so, it also provides advertising or an incentive for visit toa specified doctor or medical organization. Typically, the specifieddoctor or medical organization will be one having expertise in the samefield of medicine that employs the drug contained in the prescriptionorder.

In another example showing use by central CS 10 of its tables, itcompares prescription records in table 510A associated with a selectedEncPatID to a record in Payload Table 720 as in the foregoing example,but also determines if the NDC is “00071-0156-23” which is the NDC forthe trademarked drug Lipitor, which is known to reduce cholesterol. Ifso, the payload includes a coupon for a brand of aspirin, and printedinformation about the ability of aspirin to reduce heart disease.

Methods

FIG. 8 shows steps of methods of use.

Initially, tables storing data used by the method are populated. Thisincludes populating the Pharmacy Patient Records Table 500, and thePayload Criteria Tables 710, 720. Other data tables are also populated,including the pharmacy and retail store stock tables 550 and 620. Seestep 801.

A patient brings a prescription to the pharmacy, ordering theprescription. The PM CS 60's terminal reads the prescription data. Thedata may be entered manually using a keyboard, mouse, or any other inputdevice. The data includes patient name, drug, and quantity or dosageinformation. See step 802.

PM CS 60 generates a record in Pharmacy Patient Records Table 500. Itidentifies the PatID from the patient information, the NDC from the druginformation, assigns a PresID, and enters the order date. PM CS 60generates a RecordID and stores that in the record. See step 803.

Either PM CS 60 or a third party determines a copay amount, and PM CS 60enters that amount in the record for the prescription.

PM CS 60 generates a corresponding record in De Identified PharmacyPatient Records Table 510 from the record added to table 500. It does soby encrypting the PatID and the PresID resulting in EncPatID andEncPresID values. It also removes the Patient Information as shownsymbolically in table 510 by the blank field BF instead of a PatientInformation field. See step 804.

PM CS 60 transmits table 510 to central CS 10. See step 805.

Central CS 10 stores in table 510A the data records from table 510 andalso a RSID associated with PM CS 60 and POS CS 70. See Step 806.

Central CS 10 employs its criteria data in tables 710 and 720 todetermine what payloads to provide to the purchaser of the prescription.See step 807.

Central CS 10 saves in Combined Payload table 710 the results of itsapplication of criteria to prescription data and also save subsets ofthe data stored in table 710 in its Pharmacy PayloadID table 520A andits RS Payload table 600A. See step 808.

Central CS 10 transmits newly added records associated with the RSID forPM CS 60 in Pharmacy PayloadID table 520A to PM CS 60. PM CS 60 addsthose records to its table 520. See step 809.

Central CS 10 transmits newly added records in associated with the RSIDfor POS CS 70 in RS Payload Table 600A to POS CS 70. POS CS 70 addsthose records to its RS Payload Table 600. See step 810.

A pharmacist or the like prepares the prescription, and enters into thePM CS 60 that the prescription was filled. In response, PM CS 60 entersthe current date or date and time in the “Filled date” field in thePharmacy Patient Records Table 500. See step 811.

In response, PM CS 60 also prints information for attachment to thefilled prescription. This information includes prescription labelinformation such as patient name, medication, dosing. This informationalso includes encoding of either or both of the RecordID for theprescription and a payloadID. See step 812. In many pharmacy systems,step 812 occurs after step 803 and before step 804.

In order to generate the print including a payloadID, before printing,PM CS 60 query's Pharmacy PayloadID table 520 with any of the PresID orthe EncPresID or the NDC, or data in any of the other fields identifiedabove in table 510, for the prescription order, and retrieves from thequery for printing one or more corresponding payloadIDs. Alternatively,table 520 (and 520A) may be designed to store the PatID or EncPatID, inwhich case PM CS 60 may query based upon PatID or EncPatID for acorresponding payloadID.

In order to print the RecordID, PM CS 60 retrieves the correspondingRecordID from table 500, 510 or 520.

Someone, such as a pharmacist of a purchaser, tenders the filledprescription and associated printed information at a POS terminal 85,for purchase.

POS CS 70 reads the encoded information on the printed information atPOS terminal 85. POS CS 70 reads, for example using a bar code scannerlocated at or part of POS terminal 85 if the encoded information isencoded in a printed bar code. It may alternatively use a magnetic mediareader. The information encoded in print form on the papers associatedwith the prescription may also include a copay amount, a drugID, such asan NDC, and a department code (such as a code indicating the pharmacydepartment). See step 813.

If the information read by the POS CS 70 from the paper associated withthe filled prescription includes the copay amount, then POS CS 70includes that amount in calculating the cost of the purchasetransaction. POS CS 70 also reads at terminal 85 product identificationsfor any other products being purchased in the same purchase transaction.

Finally, POS CS 70 prints at the POS the payload or payloads identifiedfor the transaction, and prints a register receipt for the transaction.See step 814.

FIG. 9 relates to the first set of embodiments. In the first set ofembodiments, the encoded prescription information includes a payloadID.The encoded information may also include EncPatID. Upon POS CS 70reading the payloadID, it queries RS Payload table 600 to determine thecorresponding payload. See step 901.

POS CS 70 may also query table 600 to determine if the current date isbetween the values in the Date1 and Date2 fields stored in associationwith that payloadID and Payload, and only if so, print the payload. Seestep 902.

POS CS 70 then prints that payload at the POS. See step 903.

FIG. 10 relates to the second set of embodiments. In the second set ofembodiments, the printed encoded information associated with the filledprescription includes a Record ID. The recordID has a value that isunique among recordID values to only one prescription record. Upon POSCS 70 reading at POS terminal 85 a RecordID from the papers attached toor associated with the filled prescription, POS 70 transmits via datalink 80 that RecordID to PM CS 60. See step 1001. The PresID and theEncPresID may serve as a RecordID.

In response, PM CS 60 queries its Pharmacy Payload Table 520 and table500 or 510 to determine payloadID, NDC (or an equivalent drugID), copayamount and either PresID or EncPresID. PM CS 60 may also retrieve any ofthe other information from the corresponding record in De IdentifiedPharmacy Patient Records table 510. See step 1002.

PM CS 60 transmits the retrieved information via data link 80 to POS CS70. See step 1003.

PM CS 60 may also transmit to POS CS 60 the EncPatID. POS CS 70 thendetermines the payload associated in its RS Payload table 600 with thatpayloadID. See step 1004.

Again, POS CS 70 may only print the payload if it also determines thatthe current date is between the dates stored in the date1 and date2fields for that payloadID in table 600. See step 1005.

POS CS 70 then prints the payload. See step 1006.

In either of the first and second set of embodiments, the EncPatID, NDC,and copay amount, and any other information for the correspondingprescription order stored in De Identified Pharmacy Patient Recordstable 510, may be encoded in the printed material printed by the PM CS60 and read at the POS at the time of purchase. Any of the otherinformation contained in the De Identified Pharmacy Patient RecordsTable 510 may be transmitted from the PM CS 60 to the POS CS 70, eitheras print or via electronic data transfer.

In either embodiment, the POS CS 70 preferably logs some or all of thepurchase transaction data.

FIG. 11 relates to logging and use of the purchase transaction data, andto the third embodiment.

POS CS 70 logs purchase transaction data. See step 1101.

This data includes UPCs for the non prescription items being purchased,their purchase prices, the pharmacy department code, copay amount forthe filled prescription, NDC (or drugID) code for the filledprescription, the transaction total amount, identification of thepurchaser, if presented, such as frequent shopper card number, a portionof frequent shopper card number, an encrypted version of a frequencyshopper card number, a portion of credit card number used by thepurchaser during the transaction, and other information defining thetransaction. It may also include the PresID or EncPresID. The loggeddata may also include any of the other information contained in the DEIdentified Pharmacy Patient Records Table 510.

In one alternative, POS CS 70 transmits to central CS 10 logged dataincluding in association with one another for a purchase transaction,NDC or drugID, date, and EncPatID, the transmitted data may also includeany of the other information contained in the De Identified PharmacyPatient Records Table 510. See step 1102.

Central CS 10 may analyze this data and previously received data for theEncPatID from the same retail store by applying its criteria to it todetermine new payloadIDs and corresponding Payloads to associated withthe EncPatID. See step 1103.

Central CS 10 may subsequently transmit records pairs of an EncPatID anda PayloadID, or EncPatID and a Payload, to POS CS 70. See step 1104.

Each time a customer purchases a pharmacy prescription at a POS of thestore, POS CS 70 prompts the PM CS 60 for the associated EncPatID. Seestep 1105. The PM CS 60 returns the EncPatID to the POS CS 70. See step1106.

POS CS 70 then checks to determine if that EncPatID is stored inassociation with a PayloadID in its data base. See step 1107.

If so, it preferably determines if the current date is within aspecified date range. See step 1108.

If so, it then prints the payload. Se step 1109.

The retail store computer system performs all of these operations, whilethe person who presented the filled prescription for purchase is at thePOS involved in the purchase transaction including the new prescription.

As disclosed, several fields in the database tables are redundant toprovide for a single disclosure of sequence of operational steps andalternative embodiments of the methods. The actual data structures aretherefore exemplary all elements therein are clearly not required forany particular mode of operation. Moreover, the description herein ofall steps for all method embodiments does not mean all of those stepsare necessary or essential for any one embodiment. A reader shouldinstead look to the appended claims to determine the scope ofprotection.

The following table 1 presents elements of information in the PM CSassociated with a prescription record.

TABLE 1 DoctorID - Identification of a doctor associated with aprescription; NewRX - The prescription order is for a new prescription.RefillRX - The prescription order is for a refill of a prescription.Refill#RX - The number of the refill (first, second, third, etc.) of theprescription order. PaymentType - Type of payment (credit card, check,cash. etc.) Date processed - Date PatientLink printed. A PatientLink isa trademark associating with Catalina Health Resources and/or CatalinaMarketing Corporation the goods and services of “[p]romoting the sale ofhealth-related goods and services of others through the distribution ofcoupons, premiums, rebates, discounts, samples, incentives, promotions,advertisements and messages.” PatientLink herein refers to the printedmaterial associated with a prescription label containing that type ofhealth-related information. Time processed - Time PatientLink printed.NDC - An 11 digit National Drug Code Medication Name - This informationis printed on a PatientLink. May contain actual drug name. CustomerName - Patient name, which is required to personalize a PatientLink.Age - Patient age. Date of Birth - Used to calculate patient age.Gender - M - Male, F - Female, U - unknown. Script Status - N - NewScript, R - Refill Payor - Third party payer name. CASH if customerpaid. Payor Code - Third party payer code. CASH if customer paid. RXNumber - Prescription number, which is printed on a PatientLink.Dispensed Qty. - Quantity of medication dispensed, i.e. pill count.Refill Sequence - Field contains 0 for new scripts. On the first refillthis field would contain 1. Language Indicator - English or Spanishlanguage (or other language) preference. Daily Supply - Daily quantityof consumption of medication. i.e. 3 pills. Days Supply - Number of daysthis script is intended to last. Original Fill Date - This is the datethat the prescription originally got filled. Expires Date - This is thedate that the original prescription expires. Refills Remaining - Totalrefills less the ones that have already been filled. Unique Patient ID -Pharmacy system's patient identifier. Dr. Number - Dr.'s identificationnumber. Monograph - Monograph for PatientLink. State Code - State codefor store location. Region - Retailer's region. Retailer Division -Division ID to aid in triggering division specific programs. RetailerStore - Store ID to aid in triggering store specific programs. PatientDirections - Patient directions to be printed on a PatientLink.Pharmacist Directions - Pharmacist directions to be printed on aPatientLink. NCPDP ID Number - National council for prescription DrugPrograms ID. BIN No. - Third party. Control No. - Third party plan.Agency - The legal relationship between an agent and a principal.Group - Insurance that provides coverage for several people under onecontract, called a master contract. Plan - A plan document identifiesthe benefits the participants are to receive and the requirements theymust meet to become entitled to those benefits. Name Mask - A flag totell our software to mask patient name with “Valued Customer” or thelike. Medicaid - A flag to indicate if a patient is paying withMedicaid. Opt Out (HIPAA) - A flag to tell our software this patientdoes not want to receive PatientLink. Duplicate - A flag to indicate ifthis is a duplicate transaction, i.e. label only, call doctor, etc.

1. A computer implemented method for printing at a POS, comprising:determining in a PM CS of a pharmacy of a retail store a payloadIDassociate with a prescription order for a prescription ordered from saidpharmacy; filling, in said pharmacy, said prescription, to provide afilled prescription; first printing, using a PM CS printer in saidpharmacy, a first print that encodes first information associated withsaid filled prescription; attaching or physically associating withhardware or adhesive said first print with said filled prescription;during a purchase transaction in which said prescription is beingpurchased at a POS terminal of a POS CS of said retail store, readingsaid first print to determine said first information associated withsaid filled prescription; during said purchase transaction, using datalines for retrieving second information associated with said firstinformation; and during said purchase transaction, second printing,using a printer at a POS of said POS CS, a second print including saidinformation in human understandable form.
 2. The method of claim 1wherein: said first information includes a payload and said secondinformation comprises a payload associated with said payloadID in memoryof said POS CS; said retrieving comprises said POS CS retrieving saidpayload from memory of said POS CS; and said second printing comprisesprinting said payload.
 3. The method of claim 2 wherein said payloadincludes information describing safety and use of a drug contained insaid prescription.
 4. The method of claim 2 wherein said payloadincludes information providing an offer for an incentive for purchasingeither a prescription drug product or another product.
 5. The method ofclaim 1 wherein said second print includes purchase transaction data inthe form of a register receipt.
 6. The method of claim 1 wherein saidfirst information contained in said first print further comprises adrugID code for the drug identified in said prescription order, a codeindicating pharmacy department of said retail store, and pharmacyprescription recordID.
 7. The method of claim 1 wherein said firstinformation includes a recordID, and said using data lines forretrieving second information associated with said first informationfurther comprises: transmitting said recordID from said POS CS to saidPM CS; in response to receipt of said recordID sent from said POS CS tosaid PM CS, retrieving from PM CS memory retrieved data including apayloadID; in response to said PM CS retrieving from PM CS memory saidretrieved data including said payloadID, transmitting said retrieveddata from said PM CS to said POS CS so that said POS CS can determinesaid payload to print during said purchase transaction.
 8. The method ofclaim 7 wherein said payload includes information describing safety anduse of a drug contained in said prescription.
 9. The method of claim 7wherein said payload includes information providing an offer for anincentive for purchasing a either a prescription drug product or anotherproduct.
 10. The method of claim 7 wherein said retrieved data furtherincludes a drugID code for the drug identified in said prescriptionorder, a code indicating pharmacy department of said retail store, and apharmacy prescription recordID.
 11. The method of claim 7 wherein saidpayloadID is an EncPatID stored in said PM CS, and said POS CS stores inits memory payloads in association with EncPatIDs.
 12. The method ofclaim 11 further comprising: running code for transmitting from said POSCS to a central CS a log of at least part of purchase transactionsrecords each containing an EncPatID and a drugID; running code in saidcentral CS for associating EncPatIDs to payloads based upon said logrecords and criteria applicable to at least the drugIDs in said log. 13.The method of claim 1 further comprising: said PM CS transmitting deidentified patient prescription records to a central CS over a datalink; said central CS using said de identified patient prescriptionrecords to determine payloads, said central CS assigning a payloadID toeach payload; said central CS transmitting payloads and their assignedpayloadIDs to said POS CS; and said central CS assigning payloadIDs toat least one of NDCs, EncPatIDs, and EncPresIDs, and said central CStransmitting to said at least one of NDCs, EncPatIDs, and EncPresIDs andassigned payloadIDs to said PM CS.
 14. A computer network system forprinting at a POS, comprising: a PM CS, for determining in a pharmacy ofa retail store a payloadID to association with a prescription order fora prescription ordered from said pharmacy; prescription drugs withinsaid pharmacy from which said prescription order can be filled toprovide a filled prescription; a PM CS printer, in said pharmacy, forprinting a first print that encodes first information associated withsaid filled prescription; hardware or adhesive for attaching orphysically associating said first print with said filled prescription; ascanner for reading, during a purchase transaction in which saidprescription is being purchased at a POS terminal of a POS CS of saidretail store, said first print to determine said first informationassociated with said filled prescription; data lines for retrieving,during said purchase transaction, second information associated withsaid first information; and a printer at a POS of said POS CS for secondprinting, during said purchase transaction, a second print includingsaid second information in human understandable form.
 15. The system ofclaim 15 wherein: said first information includes a payloadID and saidsecond information comprises a payload associated with said payloadID inmemory of said POS CS; said data lines connect said POS CS to memory ofsaid POS CS; and said second print contains said payload.
 16. The systemof claim 15 wherein said payload includes information describing safetyand use of a drug contained in said prescription.
 17. The system ofclaim 15 wherein said payload includes information providing an offerfor an incentive for purchasing a either a prescription drug product oranother product.
 18. The system of claim 14 wherein said second printincludes purchase transaction data in the form of a register receipt.19. The system of claim 14 wherein said first information contained insaid first print further comprises a drugID code for the drug identifiedin said prescription order, a code indicating pharmacy department ofsaid retail store, and pharmacy prescription recordID.
 20. The system ofclaim 14 wherein said first information includes a recordID, and saiddata lines for retrieving said second information associated with saidfirst information further comprises: code in said POS CS having said POSCS transmit said recordID from said POS CS to said POS CS; code in saidPM CS for, in response to receipt of said recordID sent from said POS CSto said PM CS, having said PM CS retrieve from its memory retrieved dataincluding a payloadID; in response to said PM CS retrieving from PM CSmemory said retrieve data including said payloadID, transmitting saidretrieved data including said payloadID from said PM CS to said POS CSso that said POS CS can determine said payload to print during saidpurchase transaction.
 21. The system of claim 20 wherein said payloadincludes information describing safety and use of a drug contained insaid prescription.
 22. The system of claim 20 wherein said payloadincludes information providing an offer for an incentive for purchasinga either a prescription drug product or another product.
 23. The systemof claim 20 wherein said retrieved data further includes a drugID codefor the drug identified in said prescription order, a code indicatingpharmacy department of said retail store, and a pharmacy prescriptionrecordID.
 24. The system of claim 20 wherein said payloadID is anEncPatID stored in said PM CS, and said POS CS stores in its memorypayloads in association with EncPatIDs.
 25. The system of claim 24further comprising: a central CS; code in said POS CS for transmittingfrom said POS CS to a central CS a log of at least part of purchasetransaction records each containing an EncPatID and a drugID; and codein said central CS for associating EncPatIDs to payloads based upon saidlog and criteria applicable to at least drugIDs in said log.
 26. Thesystem of claim 14 further comprising: a central CS; a data ink fromsaid PM CS to said central CS; code for said PM CS transmitting deidentified patient prescription records to a central CS; code for saidcentral CS using said de identified patient prescription records todetermine payloads, code for said central CS assigning a payloadID toeach payload; code for said central CS transmitting payloads and theirassigned payloadIDs to said POS CS; and code for said central CSassigning payloadIDs to at least one of NDCs, EncPatIDs, and EncPresIDs;and code for said central CS transmitting to said at least one of NDCs,EncPatIDs, and EncPresIDs and assigned payloadIDs to said PM CS.